| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.2.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.2.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_2_2_Manage_Patient_s_Location_Within_Facility |
| Title | AS.2.2 Manage Patient's Location Within Facility (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Provide the patient's location information within a facility's premises. |
| Purpose | It is important to maintain, and/or provide access to information regarding the patient's location within a facility during an episode of care. This information can be as simple as the identification of the patient's bed assignment (e.g., John Doe1, Bed 3, Ward 2). It is also important to provide real-time information regarding the patient's location since they may receive ancillary services in multiple parts of the facility (e.g., in the physical therapy or diagnostic imaging departments). Note: The patient's location within a facility may also be revealed by viewing standard reports (such as an Emergency Department Log). The system should support viewing a patient's specific location in terms that may include campus, building, wing, unit, room, and/or bed. The system should support jurisdictional laws related to the patient's ability (or desire) to consent to disclose their location within a facility (e.g., it may be unlawful to require a minor child to sign a consent form regarding their location in a facility). The patient's location information within the facility should also be available even before the patient is ascribed to a specific provider within that facility. As such, the system may need to provide a query feature regarding the patient's location information. The system may also support the identification of the patient by alternate identifying names (e.g., John Doe1 or "J. Doe1"). For example, the patient's physical therapist may be permitted to view an elderly patient's location within a long term care facility, but the patient's pharmacist may be restricted from viewing that information. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide the patient's location information within a facility's premises.
It is important to maintain, and/or provide access to information regarding the patient's location within a facility during an episode of care. This information can be as simple as the identification of the patient's bed assignment (e.g., John Doe1, Bed 3, Ward 2). It is also important to provide real-time information regarding the patient's location since they may receive ancillary services in multiple parts of the facility (e.g., in the physical therapy or diagnostic imaging departments). Note: The patient's location within a facility may also be revealed by viewing standard reports (such as an Emergency Department Log). The system should support viewing a patient's specific location in terms that may include campus, building, wing, unit, room, and/or bed. The system should support jurisdictional laws related to the patient's ability (or desire) to consent to disclose their location within a facility (e.g., it may be unlawful to require a minor child to sign a consent form regarding their location in a facility). The patient's location information within the facility should also be available even before the patient is ascribed to a specific provider within that facility. As such, the system may need to provide a query feature regarding the patient's location information. The system may also support the identification of the patient by alternate identifying names (e.g., John Doe1 or "J. Doe1"). For example, the patient's physical therapist may be permitted to view an elderly patient's location within a long term care facility, but the patient's pharmacist may be restricted from viewing that information.
| AS.2.2#01 | SHALL |
The system SHALL provide the ability to render information regarding the patient's assigned location when the patient has an assigned location (e.g., specific bed). |
| AS.2.2#02 | dependent SHOULD |
The system SHOULD provide the ability to render information regarding a patient's location based on existing patient-consent documentation and according to scope of practice, organizational policy, and/or jurisdictional laws. |
| AS.2.2#03 | MAY |
The system MAY provide the ability to manage information regarding the patient's current location (e.g., temporary location of patient). |
| AS.2.2#05 | MAY |
The system MAY provide the ability to render information regarding the patient's current location by alternate identifiers (e.g., by arrival number, by alias, or by bed-number). |
| AS.2.2#06 | MAY |
The system MAY render the de-identified list of patients who have not consented to release of information. |
| AS.2.2#07 | SHOULD |
The system SHOULD provide the ability to render an alert if the patient has exceeded a system-defined time in a location. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.2.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide the patient's location information within a facility's premises.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>It is important to maintain, and/or provide access to information regarding the patient's location within a facility during an episode of care. This information can be as simple as the identification of the patient's bed assignment (e.g., John Doe1, Bed 3, Ward 2). It is also important to provide real-time information regarding the patient's location since they may receive ancillary services in multiple parts of the facility (e.g., in the physical therapy or diagnostic imaging departments). Note: The patient's location within a facility may also be revealed by viewing standard reports (such as an Emergency Department Log). The system should support viewing a patient's specific location in terms that may include campus, building, wing, unit, room, and/or bed. The system should support jurisdictional laws related to the patient's ability (or desire) to consent to disclose their location within a facility (e.g., it may be unlawful to require a minor child to sign a consent form regarding their location in a facility). The patient's location information within the facility should also be available even before the patient is ascribed to a specific provider within that facility. As such, the system may need to provide a query feature regarding the patient's location information. The system may also support the identification of the patient by alternate identifying names (e.g., John Doe1 or "J. Doe1"). For example, the patient's physical therapist may be permitted to view an elderly patient's location within a long term care facility, but the patient's pharmacist may be restricted from viewing that information.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render information regarding the patient's assigned location when the patient has an assigned location (e.g., specific bed).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render information regarding a patient's location based on existing patient-consent documentation and according to scope of practice, organizational policy, and/or jurisdictional laws.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to manage information regarding the patient's current location (e.g., temporary location of patient).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render information regarding the patient's current location by alternate identifiers (e.g., by arrival number, by alias, or by bed-number).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY render the de-identified list of patients who have not consented to release of information.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.2.2#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render an alert if the patient has exceeded a system-defined time in a location.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.2.2",
"version" : "2.1.0",
"name" : "AS_2_2_Manage_Patient_s_Location_Within_Facility",
"title" : "AS.2.2 Manage Patient's Location Within Facility (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Provide the patient's location information within a facility's premises.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "It is important to maintain, and/or provide access to information regarding the patient's location within a facility during an episode of care. This information can be as simple as the identification of the patient's bed assignment (e.g., John Doe1, Bed 3, Ward 2). It is also important to provide real-time information regarding the patient's location since they may receive ancillary services in multiple parts of the facility (e.g., in the physical therapy or diagnostic imaging departments). Note: The patient's location within a facility may also be revealed by viewing standard reports (such as an Emergency Department Log). The system should support viewing a patient's specific location in terms that may include campus, building, wing, unit, room, and/or bed. The system should support jurisdictional laws related to the patient's ability (or desire) to consent to disclose their location within a facility (e.g., it may be unlawful to require a minor child to sign a consent form regarding their location in a facility). The patient's location information within the facility should also be available even before the patient is ascribed to a specific provider within that facility. As such, the system may need to provide a query feature regarding the patient's location information. The system may also support the identification of the patient by alternate identifying names (e.g., John Doe1 or \"J. Doe1\"). For example, the patient's physical therapist may be permitted to view an elderly patient's location within a long term care facility, but the patient's pharmacist may be restricted from viewing that information.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2.2-01",
"label" : "AS.2.2#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render information regarding the patient's assigned location when the patient has an assigned location (e.g., specific bed).",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.4.2#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.2.2-02",
"label" : "AS.2.2#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render information regarding a patient's location based on existing patient-consent documentation and according to scope of practice, organizational policy, and/or jurisdictional laws.",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.4.2#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2.2-03",
"label" : "AS.2.2#03",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to manage information regarding the patient's current location (e.g., temporary location of patient).",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.4.2#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2.2-05",
"label" : "AS.2.2#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render information regarding the patient's current location by alternate identifiers (e.g., by arrival number, by alias, or by bed-number).",
"derivedFrom" : "EHR-S_FM_R1.1 S.1.4.2#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2.2-06",
"label" : "AS.2.2#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY render the de-identified list of patients who have not consented to release of information."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.2.2-07",
"label" : "AS.2.2#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render an alert if the patient has exceeded a system-defined time in a location."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.